CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 2

Inputs:

Sources:

sdk-nrf: PR head: 7a44701000f36969266753e45117a1c930eaa48b

Github labels

snippets
│  ├── nrf91-modem-trace-uart
│  │  │ snippet.yml

Outputs:

Toolchain

Version:
Build docker image:

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain
• ◻️ Build twister
• ◻️ Integration tests

Note: This message is automatically posted and updated by the CI

this doesn't even exist in zephyr or ncs and doesn't make sense because if it's got an nrf91 soc in then it should be using the nrf9160 soc as the name

It's coming, will be in Zephyr upstream first. @tokangas

this doesn't even exist in zephyr or ncs and doesn't make sense because if it's got an nrf91 soc in then it should be using the nrf9160 soc as the name

It's coming, will be in Zephyr upstream first. @tokangas

It needs to be added properly i.e. use the nrf91 soc so that it's build for as tmp530m/nrf9160/ns or whatnot, and conversely this PR isn't needed at all and it will just work

PR#23858 has been merged into NCS Main.
Can this PR move on now?

nRF92 support was added earlier to this snippet, but I'm wondering if we should instead have a separate snippet for it. After all, the snippet is called nrf91-modem-trace-uart. That would remove the need for checking the board in snippet.yml.